Contents
2 Storyboards
2.1 Successful EHR Transfer Request and Responses
3 Application Roles
3.1 Electronic Healthcare Record Requester - RCMR_AR010000UK01
3.2 Electronic Healthcare Record Request Fulfiller - RCMR_AR020000UK01
4 Trigger Events
4.1 Electronic Healthcare Record Request Started - RCMR_TE010000UK01
4.2 Electronic Healthcare Record Request Completed - RCMR_TE030000UK01
5 Interaction Diagrams
6 Interactions
6.1 Electronic Healthcare Record Request Started - RCMR_IN010000UK06
6.2 Electronic Healthcare Record Request Completed - RCMR_IN030000UK08
7 Message Definitions
7.1 EHR Request - RCMR_MT010101UK03
7.2 EHR Extract - RCMR_MT030101UK06
8 Glossary of Terms
9 Changes
Change History
|
In Version |
Author |
Date |
Amendment Details |
|
1.0 |
Core Technical Team |
10/05/2004 |
First Issue |
|
1.1 |
Core Technical Team |
25/06/2004 |
Updated for documentation issues |
|
1.2 |
Core Technical Team |
16/07/2004 |
Fixed broken hyperlinks |
|
1.3 |
Core Technical Team |
03/09/2004 |
Includes new generic Control Act Wrapper, new SDS OIDs and updated Agent SDS CMETs. |
|
1.4 |
Core Technical Team |
08/09/2004 |
Fixed broken hyperlinks and corrected message version numbers |
|
1.5 |
Core Technical Team |
29/10/2004 |
Updated to new versions of Infrastructure Artefacts. |
|
1.6 |
Core Technical Team |
06/12/2004 |
Updated to new versions of Infrastructure Artefacts. Change Request MIM-CR-0272 - details of these changes are given in Section 9. Removed previous section 8 - Interaction Index. |
|
1.7 |
Core Technical Team |
07/01/2005 |
Change requests MIM-CR-0146, 0235, 0274, 0296 and DACM-CR-54. Full details of changes given in section 9. |
| 1.8 |
Core Technical Team |
09/03/2005 |
Change requests MIM-CR-0303, 0442, 0445, 0446, 0447, 0448, 0449 and 0450. |
|
1.9 |
Core Technical Team |
30/09/2005 |
Change request MIM-CR-0614. |
|
2.0 |
Core Technical Team |
28/02/2006 |
Various changes to EhrExtract message and PMIM date support. See detailed change log for more details. |
|
2.1 |
Core Technical Team |
31/05/2006 |
Correct spelling mistake in "SpecimenInvestigtaion2"
element. |
|
2.2 |
Core Technical Team |
22/03/2007 |
Reorganise location of example XML files. |
1 Overview
The message definitions accessible from within this document have been defined to support transfers of Electronic Healthcare Records (EHR or Ehr) between GP Practices.
Assumptions
The following assumptions have been made with regard to this message pack:
- Anonymity of the requesting GP Practice does not need to be preserved;
- The requesting GP system is able to retrieve adequate information from both PDS and SDS in order to route a request message to the correct GP Practice where the patient's Electronic Healthcare Record is held;
- Manual processes are required at the GP Practice where the patient's Electronic Healthcare Record is held before a request is acknowledged or actioned;
- The SDS stores adequate information about a device (software system supplier, system and version etc) such that only a SDS device ID is needed in the EHR Extract message as identification for the device;
- External documents that form part of the Electronic Healthcare Record but which are not stored by the clinical system can be transferred between GP Practices via TMS, either as separate MIME-type attachments or in-line inside the EHR Extract message.
Changes since NHS GP2GP Project
- The number of messages thought to be required to support the electronic record transfer process has reduced to the two documented here.
- The EhrExtract message has been modified in a number of ways. The main reasons for making changes are:
o Alignment with clinical statement work;
o Alignment with more recently balloted HL7 material;
o Inclusion of Snomed CT coding;
o Resolution of previously outstanding issues;
o Error corrections.
2 Storyboards
2.1 Successful EHR Transfer Request and Responses
Eve Everywoman has moved out from her parents house in Manchester to a new apartment in London and soon after visits a local GP Practice, Dr Smith and Partners, to register for services. Upon registration at the new GP Practice, the GP system queries the PDS for her pre-existing GP Practice registration. It also queries the SDS for information about whether the GP system at her old GP Practice, Dr McDonald and Partners, has a NCRS compliant system. The response to this latter query is positive, enabling the GP system at Dr Smith and Partners to send an EHR Request message to the GP system at Dr McDonald and Partners.
Within 24 hours, Dr McDonald's GP system duly sends an EHR Extract message to the GP system at Dr Smith and Partners.
3 Application Roles
The applications involved in the business processes listed above play specific roles. These, along with a description of the interactions associated with each role, are identified below.
3.1 Electronic Healthcare Record Requester - RCMR_AR010000UK01
The Electronic Healthcare Record Requester is the initiator of a request for a patient's Electronic Healthcare Record.
3.2 Electronic Healthcare Record Request Fulfiller - RCMR_AR020000UK01
The Electronic Healthcare Record Request Fulfiller is receiver of an Electronic Healthcare Record Request and provider of a patient's Electronic Healthcare Record where possible.
4 Trigger Events
The trigger events which cause each interaction to be initiated are identified below.
4.1 Electronic Healthcare Record Request Started - RCMR_TE010000UK01
The Electronic Healthcare Record Request Started trigger event signals that a request to provide the patient's Electronic Healthcare Record has been made.
4.2 Electronic Healthcare Record Request Completed - RCMR_TE030000UK01
The Electronic Healthcare Record Request Completed trigger event signals that a request to provide the patient's Electronic Healthcare Record is being fulfilled by the provision of the Electronic Healthcare Record.
5 Interaction Diagrams
This section provides diagrammatic representation of which interactions are related to which application roles.
6 Interactions
6.1 Electronic Healthcare Record Request Started - RCMR_IN010000UK06
|
Sending Role |
Electronic Healthcare Record Requester |
|
|
Receiving Role |
Electronic Healthcare Record Request Fulfiller |
|
|
Trigger Event |
Electronic Healthcare Record Request Started |
|
|
Transmission Wrapper |
Send Message Payload |
|
|
Control Act Wrapper |
Control Act - Action |
|
|
Message Type |
EHR Request |
Receiver Responsibilities
|
Reason |
Interaction |
|
Request received |
Application Acknowledgement: |
6.2 Electronic Healthcare Record Request Completed - RCMR_IN030000UK08
|
Sending Role |
Electronic Healthcare Record Request Fulfiller
|
|
|
Receiving Role |
Electronic Healthcare Record Requester |
|
|
Trigger Event |
Electronic Healthcare Record Request Completed |
|
|
Transmission Wrapper |
Send Message Payload |
|
|
Control Act Wrapper |
Control Act |
|
|
Message Type |
EHR Extract |
Receiver Responsibilities
|
Reason |
Interaction |
|
EHR extract received by requester |
Application Acknowledgement: |
7 Message Definitions
This section describes each of the message types used amongst the various interactions. For each message type, links are provided to detailed documentation:
- A diagrammatic representation of the message model;
- A table view of each data field used within the message containing detailed guidance on how each field is populated together with examples;
- The schema for the message type;
- One or more example messages conforming to the schema and guidance.
7.1 EHR Request - RCMR_MT010101UK03
A message to convey a request for a patient's Electronic Healthcare Record. The request is made by a GP Practice when a patient registers with that Practice, and is sent to the GP Practice registered on the PDS for the patient at the time the new registration is made.
7.2 EHR Extract - RCMR_MT030101UK06
A message to convey a patient's Electronic Healthcare Record.
Additional detailed guidance
on implementing this message is available.
Click here to view.
Additional guidance on constructing PMIP Reports is available
here.
8 Glossary of Terms
| Data type | The structural format of the data carried in an attribute. |
| Data type flavour | A subdivision of a particular data type. |
| EHR | Electronic Healthcare Record |
| NCRS | NHS Care Record Service |
| OID | Object Identifier, a unique identifier e.g. used to identify coding systems. |
| PCT | Primary Care Trust, responsible for primary and community health services within a geographical boundary. |
| PDS | Patient Demographic Service |
| SDS | Spine Directory Services |
| Service User | A person who is registered on the PDS |
| DCE UUID | Universally Unique Identifier |